Oamp for distributed mobile architecture

ABSTRACT

A method of routing calls includes receiving a first call at a first distributed mobile architecture gateway (dMAG) from a legacy communication network. A routing path for the first call is determined based on register data associated with a mobile station, the routing path including at least one component of each of the first dMAG, a first dMA node, and a private Internet Protocol (IP) network. One or more command messages are sent to reserve the components of the first dMAG, the first dMA node, and the private Internet Protocol (IP) network. One or more confirmation messages are received indicating that components of the first dMAG, the first dMA node, and the private IP network are reserved to route the first call. The first call is connected to the mobile station via the reserved components of the first dMAG, the first dMA node, and the private IP network.

TECHNICAL FIELD

The present disclosure relates generally to distributed mobilearchitecture (dMA) systems. More specifically, example embodiments aredirected to operations, administration, maintenance and provisioning(OAMP) in a dMA system.

BACKGROUND

Distributed mobile architecture (dMA) enables multiple dMA nodes (e.g.,each dMA node including a dMA server and one or more base transceiverstations (BTSs) that service one or more mobile stations to beinterconnected via Internet Protocol (IP) connections.

This interconnectivity defines a dMA network in which voice and datacalls to and from the one or more mobile stations may be switched at theedge of the dMA network (e.g., via the dMA nodes). Thisinterconnectivity reduces a need for backhaul of traffic to a mobileswitching center (MSC) over a backhaul infrastructure that is ubiquitousin and a major contributor to high costs of the existing mobilenetworks.

Multiple dMA gateways (dMAGs) may be employed in the dMA network toprovide switching of voice and data calls to and from one or more of theplural legacy networks, including public switch telephone networks(PSTNs), IP networks, other wireless systems, and the like, whilekeeping the edge-switching efficiencies of the dMA network.

Each of the dMAGs may be associated with one or more of the multiple dMAnodes. Some or all of the dMA nodes may roam between different dMAGs.The OAMP services should be capable of servicing the changing topologyof the dMA network.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which:

FIG. 1 is a block diagram of an example distributed mobile architecture(dMA) network that includes a dMA gateway (dMAG), which provides one ormore of plural dMA nodes with service to one or more of plural legacynetworks;

FIG. 2 is a block diagram of an example embodiment of a dMA network thatincludes plural dMAGs;

FIG. 3 is a block diagram of an example dMAG in accordance with FIGS. 1and 2;

FIG. 4 is a block diagram of an example dMA node in accordance withFIGS. 1 and 2;

FIG. 5 illustrates a table showing example data associated with a dMAG,in accordance with FIGS. 1-3;

FIG. 6 is a flowchart of an example method to connect a call in the dMAnetworks of FIGS. 1 and 2;

FIG. 7 is a flowchart of an example method to connect a call in the dMAnetworks of FIGS. 1 and 2; and

FIG. 8 is a block diagram illustrating an example computer system withinwhich a set of instructions, for causing the computer system to performany one or more of the methodologies disclosed in FIGS. 1-7, may beexecuted.

DETAILED DESCRIPTION

Example embodiments are directed to operations, administration,maintenance and provisioning (OAMP) in a dMA system.

In accordance with an embodiment, there is provided a method of routingcalls via a communications network, the method comprising: receiving afirst call at a first distributed mobile architecture gateway (dMAG)from a legacy communication network, the first call placed to a mobilestation accessible via the first dMAG; determining a routing path forthe first call based on register data associated with the mobilestation, the routing path including at least one component of the firstdMAG, at least one component of a first dMA node, and at least onecomponent of a private Internet Protocol (IP) network; sending one ormore command messages to reserve the at least one component of the firstdMAG, the at least one component of the first dMA node, and the at leastone component of a private Internet Protocol (IP) network along therouting path; receiving one or more confirmation messages indicatingthat the at least one component of the first dMAG, the at least onecomponent of the first dMA node, and the at least one component of theprivate IP network are reserved to route the first call; and connectingthe first call to the mobile station the reserved at least one componentof the first dMAG, the reserved at least one component of the first dMAnode, and the reserved at least one component of the private IP network.

In accordance with another embodiment, there is provided a distributedmobile architecture gateway (dMAG), comprising: a data storage device; alegacy network interface adapted to communicate with a legacycommunication network; a home distributed mobile architecture (dMA)register including a list of a first group of dMA nodes, wherein thedMAG is designated to route calls directed to one or more mobilestations served by the first group of dMA nodes and to store performancedata associated with each dMA node of the first group of dMA nodes; avisitor dMA register including a list of a second group of dMA nodes,wherein each dMA node of the second group of dMA nodes is roaming withrespect to the dMAG and the dMAG is adapted to temporarily route callsdirected to one or more mobile stations served by the second group ofdMA nodes; a master agent adapted to receive performance data from eachdMA node of the first group of dMA nodes and each dMA node of the secondgroup of dMA nodes; and an operations module adapted to: store theperformance data from each dMA node of the first group of dMA nodes inthe data storage device; and send the performance data from each dMAnode of the second group of dMA nodes to one or more additional dMAGsvia a private IP network; wherein at least a portion of the calls routedby the dMAG are communicated via the legacy network interface.

In accordance with a further embodiment, there is provided a method ofrouting calls via a communications network, the method comprising:receiving a resource allocation query command message at a firstdistributed mobile architecture (dMA) node from a first distributedmobile architecture gateway (dMAG), the first dMA node roaming withrespect to the first dMAG and the resource allocation query beingrelated to a call directed to a mobile station adapted to communicatevia the first dMA node; sending a response message to the first dMAGfrom the first dMA node, response message indicating that one or morecomponents of the first dMA node are reserved for the call; receivingone or more packets related to the call at the first dMA node from thefirst dMAG via a private Internet Protocol (IP) network; sending one ormore signals associated with the one or more packets related to the callto the mobile stations via a wireless transceiver integrated with thefirst dMA node.

In accordance with yet another embodiment, there is provided adistributed mobile architecture (dMA) node, comprising: a data networkconnection adapted to communicate with a private Internet protocol (IP)network; and a performance module adapted to: send first performancedata to a first distributed mobile architecture gateway (dMAG) via theprivate IP network when the dMA node is in a first communication rangeof the first dMAG, the first performance data related to components ofthe dMA node and related to first calls routed via the dMA node when thedMA node is in the first communication range; and send secondperformance data to a second dMAG via the private IP network when thedMA node is in a second communication range of the second dMAG, thesecond performance data related to components of the dMA node andrelated to second calls routed via the dMA node when the dMA node is inthe second communication range; wherein the dMA node is included in ahome dMA register of the first dMAG when the dMA node is in the firstcommunication range and when the dMA node is in the second communicationrange and wherein the dMA node is included in a visitor dMA register ofthe second dMAG when the dMA node is in the second communication range.

FIG. 1 is a block diagram of an example distributed mobile architecture(dMA) network 100 that includes a dMA gateway (dMAG) 102, which providesone or more of plural dMA nodes 104, 106 and 108 with service to one ormore of plural legacy networks 112. Each of the dMA nodes 104, 106, 108may include a dMA server and one or more base transceiver stations(BTSs), which are not shown for clarity and brevity, to provide cellularcoverage site(s) to one or more mobile stations 120, 122, 124, 126, 128,130. The dMA node 104 (via its included dMA server) may hand-off of andswitch calls between BTSs that are associated with the dMA node 104. ThedMA node 104 (via its included dMA server) may further provide hand-offof calls and switch calls made between a BTS associated with dMA 104 anda BTS associated with another dMA node, such as dMA nodes 106, 108.Other dMA nodes 106, 108 may operate similarly to dMA node 104 describedabove to provide switching and hand-offs. It should be noted that thenumber of dMA nodes 104, 106, 108 shown in FIG. 1 represents only oneexample and the number of dMA nodes may be varied depending on therequirements of the dMA network 100.

The dMA nodes 104, 106, 108 are interconnected to each other via aprivate IP network 110, such as via peer-to-peer connections, to providefor the switching and hand-off efficiencies between the dMA nodes 104,106, 108 in the dMA network 100. The connections of dMA nodes 104, 106,108 to a private IP network 100 may be a wired or wireless. The dMAnodes 104, 106, 108 are also interconnected to and registered with thedMAG 102 via the private IP network 110 to provide switching of callsbetween the legacy networks 112 and the dMA nodes 104, 106, 108. In turnthe legacy networks are interconnected to the dMAG 102 via a dMAGinterface 128. The dMAG interface 128 directs call traffic between thelegacy networks 112 and the dMAG 102. The connection of the dMAG 102 tothe dMAG interface 128 may also be wired or wireless.

Although only one dMAG 102 is shown for brevity and clarity, the dMAnodes 104, 106, 108 may be mobile and may roam between different dMAGsin the dMA network 100. For example, dMA nodes 104 and 106 are home dMAnodes that are associated with and considered local to dMAG 102, whiledMA node 108 is a visitor dMA that has roamed via the private IP network110, registering with the dMAG 102. In addition, one or more mobilestations may be associated with and be considered local to a particulardMA node, while other one or more mobile stations may roam via theparticular dMA node. For example, the mobile stations 120 and 122 may belocal to the home dMA node 104, while mobile station 124 may beassociated with the home dMA node 106 and may further be roaming via thehome dMA node 104. As another example, mobile stations 128, 130 and maybe associated with the home dMA nodes 104, 106, respectively, whilemobile station 126 may be associated with the visitor dMA node 108 andmay further be roaming via the home dMA node 106.

The dMAG 102 is associated with plural dMA nodes 104, 106, 108 thatregister with the dMAG 102 and the dMAG 102 controls switching of callsbetween the legacy networks 112 and the dMA nodes 104, 106, 108 toprovide the one or more mobile stations associated with the respectivedMA nodes service to and from the legacy networks 112. The legacynetworks 112 may include a public switch telephone network (PSTN), anInternet Protocol (IP) network, one or more wireless networks, and thelike. As an example, call between the dMA network 100 and the PSTNnetwork may utilize Signaling System #7 (SS7) 114, calls between the dMAnetwork and the IP network may utilize VoIP (H.323) 116 to set up calls,and calls between the dMA network 100 and the one or more wirelessnetworks may utilize MAP/CAMEL (GSM and WCDMA), ANSI-41 (AMPS, IS-136(TDMA) and CDMA), and the like 118.

FIG. 2 is a block diagram of an example embodiment of a dMA network 200that includes plural dMAGs 202, 204, 206. The dMA nodes of each dMA nodegroup 208 (208A, 208B), 210, 212, are interconnected to each other viarespective private IP networks 214, 216, 218, such as via peer-to-peerconnections, and the private IP networks 214, 216, 218 are alsointerconnected via wired or wireless IP connections. Theinterconnections provide for the switching and hand-off efficienciesbetween the dMA nodes of the dMA node groups 208, 210, 212 in the dMAnetwork 200.

The connections of the dMA nodes in the dMA node groups 208 (208A,208B), 210, 212 to the respective private IP networks 214, 216, 218 maylikewise be a wired or wireless. Each of the dMA node groups 208, 210,212 may include one or more home dMA nodes and/or one or more visitordMA nodes. For example, dMA node group 208 is shown to include one ormore home dMA nodes 208A that are local to and registered with the homedMAG 202 and one or more visitor dMA nodes 208B that are roaming via theprivate IP network 214 and are registered with the dMAG 202.

Each of the dMAGs 202, 204, 206 is associated with and interconnected tothe dMA nodes of a respective dMA node group 208 (208A, 208B), 210, 212via a respective private IP network 214, 216, 218 to provide switchingof calls between the legacy networks 220 and the dMA nodes of therespective dMA node group 208, 210, 212. The legacy networks 220 areinterconnected to the dMAGs 202, 204, 206 via a dMAG interface 222. ThedMAG interface 222 directs call traffic between the legacy networks 220and the dMAGs 202, 204, 206. The connection of the dMAGs 202, 204, 206to the dMAG interface 222 may also be wired or wireless.

Each dMAG 202, 204, 206 may maintain or access necessary informationfrom a remote source (e.g., a remote database) to enable the respectivedMAG 202, 204, 206 to switch (connect) calls between the legacy networks220 and the dMA nodes of the respective dMA node group 208, 210, 212.Example information that may be maintained or accessed remotely mayinclude a home dMA node register for each dMAG 202, 204, 206, a visitordMA node register for each dMAG 202, 204, 206, a home location register(HLR) and a visitor location register (VLR) for each home dMA node andvisitor dMA node, and the like. Example information maintained oraccessed remotely will be described in greater detail below withreference to FIG. 5.

FIG. 3 is a block diagram 300 of an example dMAG 302 in accordance withFIGS. 1 and 2. The dMAG 302 includes a network interface 306 thatinterconnects the dMAG 302 to a private IP network 304 (e.g., private IPnetwork 110, 214, 216, 218). The dMAG 302 also includes a legacynetworks interface 310 that interconnects the dMAG 302 to one or morelegacy networks 312 (e.g., legacy networks 112, 220). Further, the dMAG302 includes a processor 308 that executes one or more of the variousmodules 316-334 stored on a memory device 314 to provide telephonyservice between the private IP network 304 (e.g., IP network 110, 214,216, 218) and the legacy networks 312 (e.g., legacy networks 112, 220).The memory device 314 includes a gateway module 316, a conversion module318, a routing module 320, a graphical user interface (GUI) module 322,a master agent module 324, one or more dMAG sub-agent modules 326, a dMAregistration module 328 and OAMP service modules 330-336 that include anoperations module 330, an administration module 332, a maintenancemodule 334 and a provisioning module 336.

Further with reference to FIG. 3, the gateway module 316 directs orcontrols call traffic from the private IP network 304 to the legacynetworks 312 (e.g., legacy networks 112, 220) via the legacy networksinterface 310. The conversion module 318 performs any conversion betweenInternet Protocol (IP) and the protocols associated with the legacynetworks 312. The routing module 320 uses the registers of FIG. 5 toroute call traffic from the legacy network 312 to the private IP network304 via the network interface 306. The GUI module 322 generates one ormore graphical user interfaces associated with the dMA network 100, 200for setting up user accounts, billing, call tracking and the like. ThedMA registration module 328 may register a home or a visitor dMA withthe dMAG 302. The master agent 324 collects or monitors the performanceof one or more components of the dMAG 302 and one or more components ofthe registered or associated dMA nodes via one or more sub-agents, andthe master agent 324 may store monitored data in the data storage device338 for later retrieval and use. More specifically, one or more dMAGsub-agents 326 may monitor the operation of one or more components ofthe dMAG 302. For example, a dMAG sub-agent 326 may be provided tomonitor the connection to the private IP network 304 via the networkinterface 306, e.g., periodically or continuously measuring throughputvia network interface 306. A dMAG sub-agent 326 may be provided tomonitor the processing speed or operation of the processor 308. Yetanother dMAG sub-agent 326 may be responsible for monitoring theremaining capacity of the data storage device 338. A dMAG sub-agent 326may also be provided to monitor the connection to the legacy networks312 via the legacy networks interface 310, e.g., periodically orcontinuously measuring throughput via network interface 310. As yetanother example, a dMAG sub-agent 326 may be provided to monitor one ormore dMA nodes (e.g., dMA nodes 104, 106, 108, dMA nodes of dMA nodegroups 208, 210, 212) registered with the dMAG 302.

Yet further with reference to FIG. 3, the operations module 330 mayanalyze the collected monitored data stored in data storage device 338to detect and report faults in the operation of the various componentsin the dMAG 302 and the dMA nodes registered or associated with the dMAG302, e.g., determining whether any component is not working optimally orhas otherwise failed. The operations module 330 may also store ormaintain fault reporting in the data storage device 338. The operationsmodule 330 may store performance data in the management information base340 for later retrieval and use. The administration module 332 maycollect accounting and billing data, e.g., managing billing data forhome and roaming accounts, generating and maintaining billing historyand call history, and the like. The maintenance module 334 isresponsible for distributing software updates for upgrades, fixes andnew feature enablement to the registered or associated dMA nodes andmobiles stations associated with the dMA nodes registered with the dMAG302. The provisioning module 336 is responsible for provisioningresources to a particular call, such as reserving or dedicating one ormore components of the dMAG 302, dMA node and private IP network 304 fora routing path that connects a call from the legacy network 312 to thedMA node associated with a receiving mobile station.

FIG. 4 is a block diagram 400 of an example dMA node 402 in accordancewith FIGS. 1 and 2. The dMA node 402 includes a network interface 406that interconnects the dMA node 402 to a private IP network 404 (e.g.,private IP network 110, 214, 216, 218). The dMA node 402 also includes awireless transceiver interface 410 that interconnects the dMA node 402to one or more wireless transceivers 412, 414, 416, each of which mayconnect one or more mobile stations (e.g., mobile stations 120-130) tothe dMA node 402 to enable wireless calls to and from the mobilestations. Further, the dMA node 402 includes a processor 408 thatexecutes one or more of the various modules 420-432 stored on a memorydevice 418 to provide telephony service between the private IP network404 (e.g., IP network 110, 214, 216, 218) and the wireless transceivers412, 414, 416 to one or more mobile stations. The memory device 418includes one or more dMA sub-agents 420, a conversion module 422, arouting module 424, a performance collection module 426, a dMAGregistration module 428, a resource allocation module 430, and amaintenance module 432.

Further with reference to FIG. 4, one or more dMA sub-agents 420 maymonitor the operation of one or more components of the dMA 402. Forexample, a dMA sub-agent maybe provided to monitor the connection to theprivate IP network 404 via the network interface 406, e.g., periodicallyor continuously measuring throughput via network interface 406. A dMAsub-agent 420 may be provided to monitor the processing speed oroperation of the processor 408. Yet another dMA sub-agent 420 may beresponsible for monitoring the remaining capacity of the data storagedevice 434. As yet another example, a dMA sub-agent 420 may also beprovided to monitor the connection to the wireless transceivers 412,414, 416 via the wireless transceiver interface 410, e.g., periodicallyor continuously measuring throughput via network interface 410. Theconversion module 422 performs any conversion between Internet Protocol(IP) and the protocols associated with the mobile stations connecting tothe dMA 402 via the wireless transceivers 412, 414, 416 (e.g., CDMA, GSMand the like). The routing module 424 uses the registers of FIG. 5 toroute call traffic from mobile stations received via the wirelesstransceivers 412, 414, 416 to the private IP network 404 via the networkinterface 406.

Yet further with reference to FIG. 4, the performance collection module426 may collect and store performance data in the storage device 436,which performance data may transmitted to the dMAG 302 periodically,continuously or on-request by the dMAG 302. The registration module 428may automatically register the dMA node 402 to a dMAG 302 when the dMAroams via a private network associated with the dMAG 302. For example,visitor dMA node 108 may automatically register with dMAG 102 when thevisitor dMA node 108 roams via the private IP network 110 associatedwith the dMAG 102. As another example, a visitor dMA node of the visitordMA node group 208B may automatically register with the dMAG 202 whenthat visitor dMA node roams via the private IP network 214 associatedwith the dMAG 202. The dMAG with which the visitor dMA node registersmay obtain that dMA node's home location register and visitor locationregister from the dMA node or the dMA node's home dMAG.

Still further with reference to FIG. 4, the resource allocation module430 of the dMA 402 may receive a request from a dMAG 302 to connect acall to a mobile station via wireless transceiver 412, 414 or 416. Inreceiving the request, the resource allocation module 430 may determinewhether it has sufficient resources to connect the call by determiningwhether there is sufficient throughput via the wireless transceiver 410,whether the processor is not overloaded, as well determining whetherthere are other pertinent constraints on the operation of the dMA node402. If the resource allocation module 430 can connect the call, itallocates resources or components for the call and informs the dMAG 302to connect the call. If the allocation module 430 cannot connect thecall due to the foregoing constrains (e.g., a large number of callscurrently connected via the dMA node 402), the allocation module 430informs the dMAG that it cannot connect the call. The maintenance module432 is responsible for receiving software or maintenance updates fromthe dMAG 302 for the dMA node and updating the memory 418 of the dMAnode 402 with the updates, and further responsible for receiving mobilestation software or maintenance updates and distributing these updatesto the mobile stations.

FIG. 5 illustrates a table 500 showing example data associated with adMAG, in accordance with FIGS. 1-3. More specifically, the table 500illustrates in a graphical format the different databases of data thatmay be utilized by the dMAGs of FIGS. 1-3 to provide switching orconnection of calls between the legacy networks and the dMA nodes(mobile stations) of FIGS. 1-3. Depending on the size of the dMA network200, 300 in FIGS. 1-3, the number of dMAGs for which data is shown inFIG. 5 may increase or decrease accordingly. The table 500 illustratesdifferent databases 508-518 each including one or more tables for alocal or 1^(st) dMAG 502 (e.g., dMAG 102, 202), a 2^(nd) dMAG 504 (e.g.,dMAG 204), and 3^(rd) dMAG 506 (e.g., dMAG 206).

The dMA node register database 508 includes a home dMA node register(e.g., one or more database tables) that identifies the dMA nodes (e.g.,104, 106, dMA nodes of dMA node group 208) which are associated with thelocal or 1^(st) dMAG 502 (e.g., dMAG 102, 202); a dMA node register(e.g., one or more database tables) of the 2^(nd) dMAG 504 (e.g., dMAG204) identifies the dMA nodes (e.g., dMA nodes of the dMA node group210) associated with the 2^(nd) dMAG 504; and a dMA node register (e.g.,one or more database tables) of the 3^(rd) dMAG 506 (e.g., dMAG 206)identifies the dMA nodes (e.g., dMA nodes of the dMA node group 212)associated with the 3^(rd) dMAG 506.

The dMA node community location register (CLR) database 510 includes thehome location register (e.g., database tables) for each of the local or1^(st) dMAG 502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504 (e.g., dMAG204) and the 3^(rd) dMAG 506 (e.g., dMAG 206). Each home locationregister of the dMA node CLR database 510 includes calling informationfor the home mobile stations that are associated respectively with thelocal or 1^(st) dMAG 502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504(e.g., dMAG 204) and the 3^(rd) dMAG 506 (e.g., dMAG 206).

The dMA node VLR database 512 includes the visitor location registers(e.g., database tables) for the local or 1^(st) dMAG 502 (e.g., dMAG102, 202), the 2^(nd) dMAG 504 (e.g., dMAG 204) and the 3^(rd) dMAG 506(e.g., dMAG 206). Each visitor location register of the dMA node VLRdatabase 512 includes calling information for the visitor mobilestations that are associated respectively with the local or 1^(st) dMAG502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504 (e.g., dMAG 204) and the3^(rd) dMAG 506 (e.g., dMAG 206).

The visitor dMA node register database 514 includes a visitor dMA noderegister (e.g., database table) that identifies visitor dMA nodes whichare associated with the local or 1^(st) dMAG 502 (e.g., dMAG 102, 202);a visitor dMA node register (e.g., a database table) of the 2^(nd) dMAG504 (e.g., dMAG 204) identifies visitor dMA nodes associated with the2^(nd) dMAG 504; and a dMA node register of the 3^(rd) dMAG 506 (e.g.,dMAG 206) identifies visitor dMA nodes associated with the 3^(rd) dMAG506.

The visitor dMA node HLR database 516 includes the home locationregister (e.g., database tables) for each visitor dMA node of the localor 1^(st) dMAG 502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504 (e.g.,dMAG 204) and the 3^(rd) dMAG 506 (e.g., dMAG 206). The home locationregister includes calling information for the mobile stations of eachvisitor dMA node that are associated respectively with the local or1^(st) dMAG 502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504 (e.g., dMAG204) and the 3^(rd) dMAG 506 (e.g., dMAG 206).

The visitor dMA node VLR database 518 includes a visitor locationregister (e.g., database tables) for each visitor dMA node of the localor 1^(st) dMAG 502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504 (e.g.,dMAG 204) and the 3^(rd) dMAG 506 (e.g., dMAG 206). Each visitorlocation register includes calling information for the visitor mobilestations of each visitor dMA node that are associated respectively withthe local or 1^(st) dMAG 502 (e.g., dMAG 102, 202), the 2^(nd) dMAG 504(e.g., dMAG 204) and the 3^(rd) dMAG 506 (e.g., dMAG 206).

FIG. 6 is a flowchart 600 of an example method to connect a call in thedMA network 100, 200. The example method begins at operation 602. Atoperation 604, a dMAG receives a connection request from a legacynetwork to connect a call to a mobile station. At operation 606, thedMAG determines a routing path based on register data associated withthe mobile station. More specifically, the dMAG may access the databasesillustrated in FIG. 5 to determine an IP address of the mobile stationthat is to receive the call and an IP addresses of a dMA node that is toconnect the call to the mobile station, as well IP addresses of routers,switches and the like to be used to connect the call between the dMAG,dMA node and the mobile station. At operation 608, the dMAG transmitsone or more command messages to reserve one or more components (e.g.,dMA, routers, switches, etc.) along the determined path to connect thecall. At operation 610, the dMAG receives one or more confirmationmessages indicating that one or more components along the routing pathhave been reserved. Thereafter, at operation 612, the dMAG connects thecall between the legacy network and the mobile station via the one ormore reserved components along the routing path. The example method endsat operation 614.

FIG. 7 is a flowchart 700 of an example method to connect a call in thedMA network 100, 200. The example method begins at operation 702. Atoperation 704, a dMA receives a resource allocation query commandmessage from a dMAG related to a call to a mobile station form a legacynetwork. At operation 706, the dMA determines whether there aresufficient resources to connect the call. If there are not sufficientresources, at operation 708, the dMA transmits a response message to thedMAG indicating that the call cannot be connected to the mobile stationvia the dMA, and at operation 718, the method 700 ends. Alternatively,if it is determined at operation 706 that there are sufficientresources, then at operation 710, the dMA transmits a response messageto the dMAG indicating that the dMA node has reserved the one or morecomponents of the dMA to connect the call. At operation 712, the dMAreceived one or more data packets related to the call from the dMAG, andat operation 714, the dMA converts the one or more received data packetsto one or more signals associated with the mobile station. Thereafter,at operation 716, the dMA wirelessly transmits the one or more signalsfrom the dMA node to the mobile station via a transceiver to connect thecall from the legacy network to the mobile station. The example methodends at operation 718.

FIG. 8 is a block diagram illustrating an example machine in the exampleform of a computer system 800 within which a set of instructions, forcausing the computer system to perform any one or more of themethodologies disclosed in FIGS. 1-7, may be executed. In alternativeembodiments, the machine operates as a standalone device or may beconnected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in server-client network environment, or as a peermachine in a peer-to-peer (or distributed) network environment. Themachine may be a personal computer (PC), a tablet PC, a Personal DigitalAssistant (PDA), a cellular telephone, a web appliance, a networkrouter, switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein.

The example computer system 800 includes a processor 802 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 804 and a static memory 806, which communicate witheach other via a bus 820. The computer system 800 may further include avideo display unit 810 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). The computer system 800 also includes analphanumeric input device 812 (e.g., a keyboard), a user interface (UI)navigation device 814 (e.g., a mouse), a disk drive unit 816, a signalgeneration device 818 (e.g., a speaker) and a network interface device808.

The disk drive unit 816 includes a machine-readable medium 822 on whichis stored one or more sets of instructions and data structures (e.g.,software 824) embodying or utilized by any one or more of themethodologies or functions described herein. The software 824 may alsoreside, completely or at least partially, within the main memory 804and/or within the processor 802 during execution thereof by the computersystem 800, the main memory 804 and the processor 802 also constitutingmachine-readable media.

The software 824 may further be transmitted or received over a network826 via the network interface device 808 utilizing any one of a numberof well-known transfer protocols (e.g., HTTP).

While the machine-readable medium 822 is shown in an example embodimentto be a single medium, the term “machine-readable medium” should betaken to include a single medium or multiple media (e.g., a centralizedor distributed database, and/or associated caches and servers) thatstore the one or more sets of instructions. The term “machine-readablemedium” shall also be taken to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of themethodologies of the present invention, or that is capable of storing,encoding or carrying data structures utilized by or associated with sucha set of instructions. The term “machine-readable medium” shallaccordingly be taken to include, but not be limited to, solid-statememories, optical and magnetic media, and carrier wave signals.

Although an embodiment of the present invention has been described withreference to specific example embodiments, it will be evident thatvarious modifications and changes may be made to these embodimentswithout departing from the broader spirit and scope of the invention.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense. The accompanying drawingsthat form a part hereof, show by way of illustration, and not oflimitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. ThisDetailed Description, therefore, is not to be taken in a limiting sense,and the scope of various embodiments is defined only by the appendedclaims, along with the full range of equivalents to which such claimsare entitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of an embodiment of the present invention. It will beevident, however, to one skilled in the art that the present inventionmay be practiced without these specific details.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments, which fall withinthe true spirit and scope of the present invention. Thus, to the maximumextent allowed by law, the scope of the present invention is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

1. A method of routing calls via a communications network, the methodcomprising: receiving a first call at a first distributed mobilearchitecture gateway (dMAG) from a legacy communication network, thefirst call placed to a mobile station accessible via the first dMAG;determining a routing path for the first call based on register dataassociated with the mobile station, the routing path including at leastone component of the first dMAG, at least one component of a first dMAnode, and at least one component of a private Internet Protocol (IP)network; sending one or more command messages to reserve the at leastone component of the first dMAG, the at least one component of the firstdMA node, and the at least one component of a private Internet Protocol(IP) network along the routing path; receiving one or more confirmationmessages indicating that the at least one component of the first dMAG,the at least one component of the first dMA node, and the at least onecomponent of the private IP network are reserved to route the firstcall; and connecting the first call to the mobile station via thereserved at least one component of the first dMAG, the reserved at leastone component of the first dMA node, and the reserved at least onecomponent of the private IP network.
 2. The method of claim 1, whereinthe register data indicates that the first dMA node is included in ahome dMA register of a second dMAG.
 3. The method of claim 2, whereinthe register data indicates that the first dMA node is roaming withrespect to the second dMAG and that the first dMA node is included in avisitor dMA register of the first dMAG.
 4. The method of claim 1,wherein the routing path is established based on call traffic dataassociated with the private IP network, the call traffic data indicatingat least a second routing path associated with a second call routed viathe private IP network.
 5. The method of claim 4, wherein the secondcall is routed from the first dMAG to a second dMA node via the privateIP network.
 6. The method of claim 5, further comprising providing aplurality of graphical user interfaces (GUIs) to display the firstrouting path, the second routing path, or any combination thereof. 7.The method of claim 1, wherein a master agent of the first dMAG sends afirst resource allocation query to the at least one component of thefirst dMAG, a second resource allocation query to the at least onecomponent of the private IP network, and a third resource allocationquery to the at least one component of the first dMA node, and whereinthe first resource allocation query is related to requesting to routethe first call via the at least one component of the first dMAG, thesecond resource allocation query is related to requesting to route thefirst call via the at least one component of the private IP network, andthe third resource allocation query is related to requesting to routethe first call via the at least one component of the first dMA node. 8.The method of claim 7, wherein the master agent of the first dMAGreceives first resource allocation data after sending the first resourceallocation query, second resource allocation data after sending thesecond resource allocation query, and third resource allocation dataafter sending the third resource allocation query and wherein the firstresource allocation data indicates the availability of the at least onecomponent of the first dMAG to route the first call, the second resourceallocation data indicates the availability of the at least one componentof the private IP network to route the first call, and the thirdresource allocation data indicates the availability of the at least onecomponent of the first dMA node to route the first call.
 9. The methodof claim 7, wherein the first resource allocation query, the secondresource allocation query, and the third resource allocation query aresent by the master agent before the first call is received at the firstdMAG or after the first call is received at the first dMAG.
 10. Themethod of claim 1, further comprising sending first configuration datato the at least one component of the first dMAG, second configurationdata to the at least one component of the private IP network, and thirdconfiguration data to the at least one component of the first dMA node,and wherein the first configuration data indicates one or more settingsof the at least one component of the first dMAG, the secondconfiguration data indicates one or more settings of the at least onecomponent of the private IP network, and the third configuration dataindicates one or more settings of the at least one component of thefirst dMA node.
 11. The method of claim 10, wherein the firstconfiguration data, the second configuration data, and the thirdconfiguration data are sent before the first call is received at thefirst dMAG or after the first call is received at the first dMAG.
 12. Adistributed mobile architecture gateway (dMAG), comprising: a datastorage device; a legacy network interface adapted to communicate with alegacy communication network; a home distributed mobile architecture(dMA) register including a list of a first group of dMA nodes, whereinthe dMAG is designated to route calls directed to one or more mobilestations served by the first group of dMA nodes and to store performancedata associated with each dMA node of the first group of dMA nodes; avisitor dMA register including a list of a second group of dMA nodes,wherein each dMA node of the second group of dMA nodes is roaming withrespect to the dMAG and the dMAG is adapted to temporarily route callsdirected to one or more mobile stations served by the second group ofdMA nodes; a master agent adapted to receive performance data from eachdMA node of the first group of dMA nodes and each dMA node of the secondgroup of dMA nodes; and an operations module adapted to: store theperformance data from each dMA node of the first group of dMA nodes inthe data storage device; and send the performance data from each dMAnode of the second group of dMA nodes to one or more additional dMAGsvia a private IP network; wherein at least a portion of the calls routedby the dMAG are communicated via the legacy network interface.
 13. ThedMAG of claim 12, further comprising a management information database(MIB), the MIB including performance requirements associated with thedMAG, the private IP network, each dMA node of the first group of dMAnodes, or any combination thereof.
 14. The dMAG of claim 13, wherein theoperations module is adapted to analyze performance data of a particularcomponent of the dMAG, a particular component of the private IP network,or a particular component of one of the dMA nodes of the first group ofdMA nodes with respect to a corresponding performance requirement toidentify when an error condition occurs with respect to the particularcomponent of the dMAG, the particular component of the private IPnetwork, or the particular component of the one of the dMA nodes of thefirst group of dMA nodes.
 15. The dMAG of claim 14, wherein theoperations module is adapted to provide error condition data indicatingan error condition with respect to the particular component of the dMAG,the particular component of the private IP network, or the particularcomponent of the one of the dMA nodes of the first group of dMA nodes.16. The dMAG of claim 15, wherein the error condition data includes amessage to re-route a particular call.
 17. The dMAG of claim 15, whereinthe error condition data is sent to a technician, an error log stored atthe dMAG, or both.
 18. The dMAG of claim 12, wherein the performancedata relates to a plurality of performance metrics.
 19. The dMAG ofclaim 12, wherein the master agent is adapted to receive the performancedata from one or more sub-agents of each component of the dMA nodes ofthe first group of dMA nodes.
 20. The dMAG of claim 19, wherein themaster agent, the one or more sub-agents of each component of the dMAnodes of the first group of dMA nodes, and the MIB communicate accordingto simple network management protocol (SNMP).
 21. The dMAG of claim 19,wherein the master agent, the one or more sub-agents of each componentof the dMA node of the first group of dMA nodes, and the MIB communicateaccording to agent-X protocol.
 22. The dMAG of claim 12, furthercomprising a maintenance module adapted to send software to the dMAnodes of the first group of dMA nodes.
 23. The dMAG of claim 22, whereinthe software includes updates to previous versions of software executedby the dMA nodes of the first group of dMA nodes.
 24. The dMAG of claim22, wherein the software replaces previous versions of software executedby the dMA nodes of the first group of dMA nodes.
 25. The dMAG of claim22, wherein the maintenance module is adapted to produce a backup copyof data stored in the MIB.
 26. The dMAG of claim 13, wherein theperformance data is stored in the MIB, the data storage device, or anycombination thereof.
 27. The dMAG of claim 12, wherein the legacycommunication network is a public switched telephone network (PSTN), anintegrated services digital network (ISDN), a wide-area wirelessnetwork, or a public IP network.
 28. The dMAG of claim 12, wherein theperformance data is associated with a wireless transceiver interface ofeach dMA node of the first group of dMA nodes, a wireless transceiverinterface of each dMA node of the second group of dMA nodes, a wirelesstransceiver of each dMA node of the first group of dMA nodes, a wirelesstransceiver of each dMA node of the second group of dMA nodes, a datanetwork connection of each dMA node of the first group of dMA nodes, adata network connection of each dMA node of the second group of dMAnodes, or any combination thereof.
 29. The dMAG of claim 12, wherein thedMAG includes a graphical user interface (GUI) module adapted to produceat least one GUI related to presenting the performance data of each dMAnode of the first group of dMA nodes, managing components of each dMAnode of the first group of dMA nodes, managing components of the privateIP network, presenting a configuration of a particular component of adMA node of the first group of dMA nodes, presenting a configuration ofa particular component of the dMAG, presenting a configuration of aparticular component of the private IP network, or any combinationthereof.
 30. The dMAG of claim 29, wherein the at least one GUI isaccessible via a display device coupled to the dMAG.
 31. The dMAG ofclaim 29, wherein the at least one GUI is accessible via a displaydevice located remotely from the dMAG.
 32. The dMAG of claim 29, whereinthe at least one GUI is accessible via an Internet portal.
 33. The dMAGof claim 29, wherein the at least one GUI is configured according to anapplet executable via a web browser.
 34. The dMAG of claim 12, whereinthe master agent is adapted to query at least one component of aparticular dMA node of the first group of dMA nodes for specifiedperformance data.
 35. The dMAG of claim 12, wherein the dMAG includes anadministration module adapted to generate and store billing informationassociated with calls directed to the one or more mobile stations servedby the first group of dMA nodes.
 36. The dMAG of claim 12, furthercomprising a provisioning module adapted to reserve resources of thedMAG, resources of the private IP network, resources of at least one dMAnode of the first group of dMA nodes, resources of the at least one dMAnode of the second group of dMA nodes, or any combination thereof, toroute calls from the dMAG to the at least one dMA node of the firstgroup of dMA nodes, to the at least one dMA node of the second group ofdMA nodes, or both, based on the performance data.
 37. A method ofrouting calls via a communications network, the method comprising:receiving a resource allocation query command message at a firstdistributed mobile architecture (dMA) node from a first distributedmobile architecture gateway (dMAG), the first dMA node roaming withrespect to the first dMAG and the resource allocation query beingrelated to a call directed to a mobile station adapted to communicatevia the first dMA node; sending a response message to the first dMAGfrom the first dMA node, response message indicating that one or morecomponents of the first dMA node are reserved for the call; receivingone or more packets related to the call at the first dMA node from thefirst dMAG via a private Internet Protocol (IP) network; sending one ormore signals associated with the one or more packets related to the callto the mobile stations via a wireless transceiver integrated with thefirst dMA node.
 38. The method of claim 37, wherein the one or morecomponents of the first dMA node are reserved based on call traffic dataat the first dMA node.
 39. The method of claim 38, wherein the calltraffic data relates to one or more additional calls routed via thefirst dMA node.
 40. The method of claim 39, further comprisingdetermining that insufficient resources are available at the first dMAnode to route a particular additional call directed to an additionalmobile stations adapted to communicate via the first dMA node.
 41. Themethod of claim 40, wherein the first dMA node sends an indication tothe first dMAG that the particular additional call cannot be routed tothe additional mobile station via the first dMA node.
 42. The method ofclaim 37, wherein the first dMA node is included in a home dMA registerof a second dMAG.
 43. The method of claim 37, further comprisingconverting the one or more packets related to the call to one or moresignals compatible with the mobile station.
 44. A distributed mobilearchitecture (dMA) node, comprising: a data network connection adaptedto communicate with a private Internet protocol (IP) network; and aperformance module adapted to: send first performance data to a firstdistributed mobile architecture gateway (dMAG) via the private IPnetwork when the dMA node is in a first communication range of the firstdMAG, the first performance data related to components of the dMA nodeand related to first calls routed via the dMA node when the dMA node isin the first communication range; and send second performance data to asecond dMAG via the private IP network when the dMA node is in a secondcommunication range of the second dMAG, the second performance datarelated to components of the dMA node and related to second calls routedvia the dMA node when the dMA node is in the second communication range;wherein the dMA node is included in a home dMA register of the firstdMAG when the dMA node is in the first communication range and when thedMA node is in the second communication range and wherein the dMA nodeis included in a visitor dMA register of the second dMAG when the dMAnode is in the second communication range.
 45. The dMA node of claim 44,further comprising a wireless transceiver interface, a processor, amemory, a data storage device, or any combination thereof.
 46. The dMAnode of claim 45, further comprising one or more sub-agents adapted tomonitor the performance of the data network connection, the wirelesstransceiver interface, the processor, the memory, the data storagedevice, or any combination thereof.
 47. The dMA node of claim 44,further comprising a configuration module adapted to: storeconfiguration data related to the data network connection, the wirelesstransceiver interface, the processor, the memory, the data storagedevice, or any combination thereof, and receive configuration datarelated to the data network connection, the wireless transceiverinterface, the processor, the memory, the data storage device, or anycombination thereof, from the first dMAG.
 48. The dMA node of claim 44,further comprising a maintenance module adapted to receive softwareupdates from the first dMAG, the software updates related to the datanetwork connection, the wireless transceiver interface, the processor,the memory, the data storage device, or any combination thereof, and thesoftware updates based on the first performance data, the secondperformance data, or any combination thereof.